(Item 8218) DLUR processing of short RSP(BIND) RUs
--------------------------------------------------
DLUR testing uncovered a condition not described in the
architecture, specifically how the DLUR BF should process short
RSP(BIND) RUs.  The RSP(BIND) format does describe an extended
short response to a nonnegotiable BIND, but the DLUR can receive
an even shorter response, and there is currently no direction on
how to process it.
 
NCP BF takes a short RSP(BIND) and converts it into an extended
short RSP(BIND).
 
What needs clarification in the DLUR architecture is how to
convert a short RSP(BIND) into an extended short RSP(BIND).
 
The document will be updated to include the following:
 
    The short +RSP(BIND) is converted into an extended short form
    RSP(BIND) by:
 
       - zeroing 31 (X'1F') bytes for the extended short form
         RSP(BIND)
       - setting the RU code to BIND (X'31')
       - setting the BIND type to nonnegotiable
       - including the SLU max send size and the PLU max send size
         from the BIND request
       - setting the whole-BIUs required indicator on if the
         RSP(BIND) will be reextended
       - setting the pacing fields in the RSP(BIND) according to
         normal negotiation rules for the PLU stage:
            * if the ASP indicator will be set to 1, then set the
              one-stage pacing indicators and zero out the pacing
              window size fields
            * if the ASP indicator will be set to 0, then set the
              pacing window size fields to the BIND request values
       - setting the limited resource bit if the link station is a
         limited resource link (LU 6.2 RSP(BIND)s only)
 
    and the pacing values for the SLU stage are saved so that fixed
    session pacing will be used with the window sizes specified in
    the BIND request.